Ah, sorry... This article wasn't published because the date uses a future date:

https://github.com/ruby/www.ruby-lang.org/actions/runs/17788666874/job/50560893546#step:5:13

          Skipping: en/news/_posts/2025-09-18-dos-rexml-cve-2025-58767.md has a future date

@hsbt Could you re-run the job tomorrow (2025-09-18T12:00:00+09:00) or later?

or simply modified publish data like 2025-09-17T6:00:00+09:00? I'm okay to re-run at today's night.

@naitoh Which approach do you prefer?

@hsbt @kou

Could you re-run the job tomorrow (2025-09-18T12:00:00+09:00) or later?

Please, this.

The publish date is 2025-09-18 03:00:00 +0000. It means this advisory will publish 9/18 12:00 JST. I'm not sure that time is intentional. But I will re-run that after 12:00 JST today.

Yes. The publish date isn't strictly correct. We just don't care about strict date.

FYI: We can merge any other PR such as #3623 instead of re-run the job to publish this article.

https://www.ruby-lang.org/en/news/2025/09/18/dos-rexml-cve-2025-58767/ is published now.

Thanks!